Method and system for building/updating grammars in voice access systems

ABSTRACT

A method and system for building/updating grammars in voice access systems is disclosed. The method includes receiving a grammar update request from a voice access system, retrieving data, filtering the data and providing the filtered data to the voice access system. The grammar update request identifies a navigation context of a user interface provided by a data system. The user interface provides access to information in the data system. The data is retrieved from the data system and pertains to the navigation context. The filtering is performed to obtain filtered data pertaining to user interface (UI) objects enabled for grammar updates.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application is a continuation of U.S. patent application Ser. No. 10/131,369, filed on Apr. 23, 2002, now U.S. Pat No. 7,149,694 entitled “METHOD AND SYSTEM FOR BUILDING/UPDATING GRAMMARS IN VOICE ACCESS SYSTEMS” ; which claims the benefit of U.S. Provisional Application No. 60/356,713, filed on Feb. 13, 2002, entitled “METHOD AND SYSTEM FOR ENABLING VOICE CONNECTIVITY TO A DATA SYSTEM.” These applications are incorporated by reference herein in its entirety and for all purposes.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to voice access to data systems in general, and a method and system for updating grammars that are used in voice access systems in particular

2. Background Information

Recently, the development of new technologies in the telephony and speech recognition areas has enabled data systems to be accessed. via voice (e.g., spoken verbal input). Such voice-enabled data systems let users navigate to request a particular piece of data or a related set of data using voice commands, and then “reads back” the data to the user. These types of data systems are widely used in information systems in various industries, including banking, insurance, investments, etc.

In general, .in order to provide voice access to a data system, a complete voice interface must be provided. This typically involves integrating various hardware and software components, such as telephony interfaces, multi-channel access equipment, speech recognition software, text-to-speech (TTS) software and hardware, and other related components. A fundamental aspect of the a voice access system concerns the grammar used by the system. A grammar is a specification of all allowed user utterances (syntax) in an application, such as those used a voice application, which contains the logic for enabling interactions between a voice interface and a data system. A grammar also contains the meanings of each key word or phrase (semantics) corresponding to the user utterances.

Typically, a grammar will include information pertaining to specific data in the data system that is accessed via the voice interface. For example, if a voice access system is to include access to contact information, the grammar will generally include specific contact information, such as last name, first name, address, etc. This information is used to disambiguate between different user utterances. For instance, suppose a desired contact name is Laura Smith, and the data system includes contacts named, Laura Smith, Lauren Smith, Lori Smith and Lorna Smith. Since each of these names sounds similar but are different, there needs to be specific grammar information for each name.

Another aspect of grammars concerns performance. In order to provide adequate performance, grammar information will generally be stored locally (i.e., on a server that is local to a voice application). In some implementations, the grammar is stored in a pre-compiled format for further performance enhancement. To support these architectures, it is necessary to first provide an initial set of grammar information pertaining to data in the data system, and then periodically update the grammar information to reflect changes in the data in the data system. Typically, this grammar update process will require a specific grammar update module or application to be written for each voice application.

Several vendors now provide integrated voice-access systems that handle the voice-to-computer aspects of a voice-enabled data system. For example, these integrated systems handle telephony connectivity to a phone network, perform speech recognition to convert voice commands and verbalized data requests to a computer-readable form (e.g., ASCII text or binary text form), and handle the TTS functions. Although these integrated voice-access systems provide a lot of the workload, they still require grammars to be written and updated to enable access to the data system.

SUMMARY OF THE INVENTION

A method and system to update grammar information in a voice access system that provides access to a data system. A user interface (UI) is provided to enable an administrator to select UI object pertaining to a user interface provided by the data system to provide grammar update support for. The data system UI interface corresponds to a user interfaced that users would see if using a “normal” computer client connection to the data system. The user interface comprises a hierarchy of screens, views, applets (i.e., forms), columns, and fields. XSLT style sheets are built based on the UI objects that are selected to provide grammar update support for. A grammar update request may then be submitted to the system that identifies a navigation context of the data system UI, a style sheet to apply, and an optional last update value corresponding to when the navigation context was last updated. For example, it may be desired to update all fields in a form that have been selected for grammar updating. In response to receiving the request, the system retrieves data from the data system pertaining to the navigation context; and filters the data using the identified style sheet and the last update value to remove data pertaining to UI objects in the navigation context that were not selected to have grammar update support for. If a last update value is provided, the filter also filters out all data except for values that have changed (i.e., been updated, added, or delected) since the last update. The filtered data are then sent back to the voice access system to update its grammar.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic block diagram illustrating an exemplary architecture to enable grammar data to be updated to support voice access to an enterprise data system in accordance with one embodiment of the invention;

FIG. 2 is a block schematic diagram illustrating a multi-layer software architecture in accordance with one embodiment of the invention;

FIG. 3 is a block schematic diagram illustrating further details of the multi-layer software architecture of FIG. 2;

FIG. 4 is a block schematic diagram illustrating further details of various object manager objects in accordance with the multi-layer software architecture;

FIG. 5 is a block schematic diagram illustrating further details of a business component as used in the multi-layer software architecture;

FIG. 6 is a block schematic diagram illustrating further details of the architecture of FIG. 1.

FIG. 7 is a block schematic diagram illustrating details of a voice metadata builder component in accordance with one embodiment of the invention;

FIG. 8 is a flowchart illustrating the operations and logic used by the invention when enabling an administrator to specify which UI objects to voice enable and/or provide grammar update support for and the generation of an application representation to be used for building style sheets in accordance with one embodiment of the invention;

FIG. 9 is a code listing corresponding to an exemplary portion of a repository file;

FIG. 10 is a block diagram illustrating the user interface (UI) hierarchy of a user interface to enable access to -the enterprise data system in accordance with one embodiment of the invention;

FIG. 11 is a representation of an exemplary user interface corresponding to a Sales Accounts view;

FIG. 12 shows a portion of an application representation that corresponds to the Sales Accounts view of FIG. 11 and corresponding subscription data;

FIG. 13 is a representation of a graphical user interface window that enables an administrator to select UI objects to provide grammar update support for;

FIG. 14A-C collectively comprise a combination of a style sheet layout definition and integrated flowchart corresponding to an exemplary style sheet that-is used to filter out data that does not pertain to grammar update-enabled fields;

FIG. 15 is a flowchart illustrating the operations and logic implemented by the invention when generating a style sheet in accordance with one embodiment of the invention;

FIG. 16 is an XML listing illustrating a typical format of an XML output document that is returned to a voice application in accordance with one embodiment of the invention.

FIG. 17 is an outlined XML listing having a format corresponding to the XML listing of FIG. 16 to illustrate the various hierarchical levels of the XML output document;

FIG. 18 is an XML code portion listing illustrating details of an RS_HEADER section of the XML output document;

FIG. 19 is an XML code portion listing illustrating details of an RS_DATA section of the XML output document;

FIG. 20 is a flowchart illustrating the operations and logic used by one embodiment of the invention when providing a grammar update;

FIG. 21 is a block schematic diagram illustrating an exemplary hardware infrastructure for implementing one embodiment of the invention; and

FIG. 22 is a schematic diagram illustrating various components of an exemplary computer server system that may be used for the various computer servers in the hardware infrastructures of FIG. 21.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS

A system and method for enabling voice connectivity to a data system is described in detail herein. In the following description, numerous specific details are disclosed, such as exemplary software and system architectures, to provide a. thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, etc. In other instances, well-known structures or operations are not shown or described in detail to avoid obscuring aspects of various embodiments of the invention.

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

A high-level architecture 10 in accordance with one embodiment of the invention is shown in FIG. 1. At the center of architecture 10 is a mobile connector interface 12 that enables third parties (referred to herein as “Voice vendors”) to develop voice applications 14 that enable users to verbally access data stored in an enterprise data system 16 via a phone 18. In further detail, a user of phone 18 is connected to a voice infrastructure component 20 via a phone network 22, such as a wireless phone network, land-line phone network, or the combination of the two. The voice infrastructure includes various hardware and software components that enable users to interact with voice application 14 via voice commands. Typically, these components will include a telephony interface 24, an automated speech recognition (ASR) component 26, and a text-to-speech (TTS) component 28. In one embodiment, voice application 14 uses a standard application programming interface 30 that enables the voice application to interact with voice infrastructure 20 using a predefine set of commands and data protocols specific to various voice access products. At present, several vendors provide voice access products that provide operations and services corresponding to voice infrastructure 20, including Avaya corporation (formerly Lucent) (telephony interfaces/PXB switching) and Nuance corporation, Salt Lake City, Utah (speech recognition software).

Generally, a voice access system will employ a set of grammars that are stored in a manner in which grammar information can be readily retrieved by the system. Typically, the grammar information may be stored in a local database or file system, a depicted by grammar database 31 in the FIGS. herein.

The specific details and inner-workings of the voice infrastructure is beyond the scope of the invention. For the purpose of implementing the voice infrastructure, it is assumed that an integrated voice access system will be deployed and/or the IT professionals who implement the system have sufficient knowledge and skill to set up the voice infrastructure using readily available hardware and software components, such as those described above.

In one embodiment, mobile connector interface 12 provides a mechanism for interacting with enterprise data system 16 via XML (extended markup language) data in accordance with predefined protocol and data formats that define parameters pertaining to the transferred XML data-. These data include incoming XML data 32, which typically comprise XML data prescribing a data request that is received by enterprise data system 16, and outgoing XML data 34, which typically comprises XML data pertaining to data returned in response to the data request by enterprise data system 16.

In one embodiment, enterprise data system 16 includes an application server 36, which logically represents a collection of (generally) distributed software components and modules that define the business logic to enable external systems and users to access various data stored in a database 38 that hosts the data for the enterprise data system based on a pre-defined set of interfaces. Further details of the software components and modules corresponding to application server 36 are described below.

Typically, the enterprise data system will provide various means to access the data that it stores, such as client connections, as will be understood by those skilled in the database/data system arts. Ideally, it is desired to enable voice access to the enterprise system in a manner that is substantially transparent to it. In one embodiment, each connection provided by the mobile connector appears to the enterprise data system as a “normal” client connection, and as such, does not require any changes to the core software components that support the enterprise data system.

In one embodiment, software corresponding to core software components that control normal operations of enterprise data system 16 (i.e., operations involving interaction with the enterprise data system outside of voice access operations) can be logically structured as a multi-layered architecture 50, as shown in FIG. 2. In one embodiment, the logical multi-layered architecture provides a platform for common services 52 to support various applications that implement the architecture. These services may be logically partitioned into a user interface layer 54, an object manager layer 56, a data manager layer 58, and a data exchange layer 60.

In one embodiment, user interface layer 54 provides the screens, views, and applets that make up various user interfaces that are rendered on client machines that connect to the enterprise data system via a computer network based client connection to enable users of those client machines to interact with the enterprise data system. Generally, user interface layer 54 may be configured to support various types of clients, including traditional connected clients, remote clients, thin clients over an Intranet, Java thin clients or non-Windows-based operating systems, and HTML clients over the Internet, etc.

Object manager layer 56 is designed to manage one or more sets of business rules or business concepts associated with one or more applications and to provide the interface between user interface layer 54 and data manager layer 58. In one embodiment, the business rules or concepts can be represented as business objects. In one embodiment, the business objects may be designed as configurable software representations of the various business rules or concepts applicable to the data services provided by embodiments of the invention disclosed herein, as explained below in further detail.

Data manager layer 58 is designed to maintain logical views of underlying data stored in one or more databases 62 (e.g., database 38) corresponding to a data storage layer 64, while allowing the object manager to function independently of the underlying data structures or tables in which data are stored. In one embodiment, the data manager provides certain database query functions, such as generation of structure query language (SQL) in real time to access the data. In one embodiment, data manager 68 is designed to operate on object definitions 66 stored in a repository file 68 corresponding to a database schema used to implement the data model for the system, as described in further detail below. Generally, the data exchange layer is designed to handle the interactions with one or more specific target databases and provide the interface between the data manager and those databases, via either generic (e.g., Open Database Connectivity (ODBC)) or native (e.g., Oracle Connection Interface (OCI)) database interface protocols.

FIG. 3 shows a block diagram illustrating another logical representation of a multi-layered architecture corresponding to the core operations of the enterprise data system. Again, the multi-layered architecture as illustrated in FIG. 3 provides the platform for various common services designed and configured to support the various core operations provided by the enterprise data system. In one embodiment, these various services include a presentation services layer 70 corresponding to services provided by an applet manager and user interface 72, an application services layer 74 corresponding to services provided by object manager layer 56 and data manager layer 58, and a data services layer 76 corresponding to services provided by database 62.

In one embodiment, presentation services 70 may be designed and configured to support various types of clients and may provide them with user interface screens, views and applets. In one embodiment, application services 74 may include business logic services and database interaction services. In one embodiment, business logic services provide the class and behaviors of business objects and business components implemented by the application services. In one embodiment, database interaction services may be designed and configured to take the user interface (UI) request for data from a business component and generate the appropriate database commands (e.g., SQL queries, etc.) to satisfy the request. For example, the data interaction services may be used to translate a call for data into RDBMS-specific SQL statements.

A multi-layer architecture illustrating the relationships between business objects, business components, and database tables is shown in FIG. 4. A business object 80 sitting at the top layer passes various data access requests to business components 82, 84, and 86 to retrieve data pertaining to the business object from a database 88. For example, business object 80 may pertain to an contact object and business components 82, 84, and 86 are used to access data in a database 62 pertaining to contacts.

In one aspect, business components are objects that span data from one or more physical database tables and calculated values by referencing a base table and explicitly joining and linking other tables, including intersection tables, as depicted by tables 90-1 and 90-2, each of which include a plurality of records 92. As explained in further detail below, each business component contains information for mapping to various data stored in those tables. More specifically, these mappings are between a requested object, such as a subject, and information pertaining to that object that are stored in the database table(s) to which the business component corresponds. In one embodiment, database schema information stored in repository file 68 is used by the business components in determining their table mappings.

A block diagram of a logical structure of a business component in accordance with one embodiment of the present invention is shown in FIG. 5. Each business component (e.g., 82, 84, 86) may include a set of properties 95 that pertain to the respective business component (e.g., NAME, which specifies the logical name of the business component, TABLE NAME, which specifies the actual name of the underlying table, etc.). A business component also includes a set of fields 96, each of which may have a set of associated attributes or properties 98. For example, a field may include a NAME property that identifies the name of the field, a COLUMN NAME property that identifies the column of the underlying table to which the respective field is mapped, etc.

An architecture 100 illustrating further details of mobile connector interface 12 and other related components is shown in FIG. 6. The mobile connector interface comprises two separate but related components, including a Voice Metadata Builder 102 and a Voice Update Support component 104. The Voice Metadata Builder is an administrative tool that will generally be run during an initial installation and may be run again if the object definitions 66 stored in the repository file have changed. The Voice Update. Support component is a runtime component that is run at the discretion of voice application 14, as explained below in further detail.

In addition to Voice Metadata Builder 102 and Voice Update Support component 104, architecture 100 further includes a Web engine 106, a reference or Voice vendor GUI (graphical user interface) component 108, a Siebel COM or Java interface 110 and an HTTP(S) interface 112. Web engine 106 is used to provide an interface between voice application 14 and common services 52 via either Siebel COM or Java interface 110 or HTTP(S) interface 112. In one embodiment, Web engine 106 provides an XML interface that enables application server 36 to receive incoming XML data 32 and send outgoing XML data 34.

The reference or Voice vendor GUI in combination with the voice metadata builder enables the Voice vendor to select which screens, views, applets, columns, and controls/fields voice application 14 may access through appropriate XML queries that are submitted as incoming XML data 32 to Web engine 106. Further details of Voice Metadata Builder 102 are shown in FIG. 7. At the core of the Voice Metadata Builder is a Metadata Builder Engine 114, which includes a parser 116, and an extractor 118. Additional components include an XML builder 120 and a style sheet builder 122. In one embodiment, voice metadata builder 102 may be implemented as a business service that is managed by object manager 56.

With reference to FIG. 8, the process for selecting which UI objects to voice enable and for generating style sheets begins in a block 300 in which the Voice vender user (e.g., an administrator) opens reference or Voice vendor GUI 108, initiates the voice enable process, and selects an application the administrator would like to provide voice access to. Generally, the administrator will be presented with a user interface such as a dialog box or web page (both not shown) that enables the user to select an application to voice enable from among one or more applications that are supported by the enterprise data system.

Upon selection of the application, selection data 123 identifying the selected application is pass to metadata builder engine 114, which then invokes extractor 118 to traverse repository file 68 and extract metadata corresponding to the selected application's UI objects and definitions in a block 302. As described above, the repository file contains object definitions for the various objects corresponding to all of the applications in the enterprise data system, stored as metadata in a compiled format. Included in these object definitions are user interface object definitions and their relationships. An exemplary portion of a repository file is shown in FIG. 9. (It is noted that in one embodiment the repository file is actually stored in a compiled format rather than the ASCII text format shown in FIG. 9, which is used in the figure for clarity.)

In one embodiment, the user interface objects have a hierarchical relationship, as shown in FIG. 10, wherein the top level of the hierarchy corresponds to the entire enterprise:data system, as depicted by an enterprise data system block 150. Each enterprise data system will include one or more applications 152, with each application 152 including a plurality of screen 154. In turn, each screen will include one or more views 156, with each view including one or more applets 158. Finally, each applet will include a plurality of columns and/or fields/controls 160, with each column corresponding to column in a list applet each field/control typically comprising an edit control on a detail form (i.e., entry) applet that is either mapped to a column in a database table or a list of values that are either predefined, or generated at run-time based on current data in the enterprise data system.

A rendered user interface 170 that graphically depicts the UI object hierarchy of FIG. 10 is shown in FIG. 11. User interface 170 includes a screen bar 170 corresponding to screens 154 that enables a user to select a screen the user desires to view. For example, and the illustrated user interface these screens include a “Home” screen 172, an “Opportunities” screen 174, and “Accounts” screen 176, a “Contacts” screen 178, an “Activities” Screen 180, a “Calendar” screen 182, a “Quotes” screen 184, a “Forecasts” screen 186, and a “Revenues” Screen 188. Activation of the tab having the screen name causes the application to render the selected screen and navigate the user to the application “domain” corresponding to the selected screen.

As discussed above, each screen includes one or more applets. Under common user interface terminology, applets would generally fall into the form category. Applets generally have two formats: list applets and form applets. A list applet contains a tabular list of data including multiple rows and data columns similar to that shown in an Account list applet 190. A form applet typically includes a plurality of fields containing data pertaining to a particular “record,” wherein the record will often correspond to a selected row in an accompanying list applet. For example, an Account entry applet 192 includes a “Name” field 194, and “Address Line 1” field 196, and “Address Line 2” field 198, a “Zip” field 200, a “Main Phone #” field 202, a “City” field 204, a “State” field 206, a “County” field 208, an “Account Type” filed 210, a “Status” filed 212, an “Industries” field 214, a “Territories” field 216, and “Account Team” field 218 and a “Parent” field 220. Generally, each field will have a corresponding edit control, which typically will comprise an edit box or a dropdown control from which a user may select from a predetermined list of values. In some instances, a dialog picklist control 222 may also be provided that enables a user to select from list of options via a dialog box that is populated with the list using a run-time query.

In many instances, applets may be linked via a parent-child type relationship. For example, Account list applet 190 is a parent of Account entry applet 192, which includes a plurality of tabs 224 to enable a user to enter or view information specific to the name on each tab and the currently selected account record. For example, the currently selected account is “A & W Gifts and Flowers,” and a user could enter information concerning contacts for this account by activating a “Contacts” tab 226, which would bring up a Contacts form including a plurality of fields pertaining to contact information (not shown).

Returning to the flowchart of FIG. 8, in a block 304 parser 116 builds an application representation 124 comprising an internal representation of the selected application's screens, views, applets, columns, and fields/controls based on the corresponding user interface object definition metadata that was extracted in block 302, as depicted by application representation 124. In one embodiment, the application representation comprises a hierarchical tree structure of the object definitions extracted by the extractor. In exemplary application representation occupies the left-hand portion of FIG. 12. Each node in the hierarchical tree stores data corresponding to an application representation object. The object may be an application object, screen object, view object, applet object, etc. After getting the object definition from the extractor, the parser will convert the object to an application representation object and store it in a node of the hierarchical tree structure. This is repeated for all objects until the tree is filled.

Next, in a block 306 metadata builder engine 114 invokes XML builder 120 to build an XML data tree 126 corresponding to application representation 124, and returns the XML data tree to reference or Voice vendor GUI 108 in a block 308. To perform this operation, the XML builder traverses the hierarchical tree and builds an XML representation for it. The reference or Voice vendor GUI parses the XML data tree and renders a selection tree 130 in a window or frame similar to that shown in FIG. 13. In general, the selection tree will have a hierarchy similar to the user interface hierarchy of the application, as defined by application representation 124.

In one embodiment, the reference GUI comprises a plurality of ASP (Active Server Page) web pages that use an ActiveX data control to get access to the voice metadata builder. In this embodiment, the ASP creates the ActiveX control, gains access to the voice metadata builder, starts the XML extraction to get the XML object definition, renders the HTML for the reference GUI, returns subscription XML data for UI components to voice enable and/or provide voice update support for, triggers the creation of style sheets, and allows loading and saving existing subscriptions. In one embodiment, the ActiveX DataControl is used to create UI window 130, wherein the ActiveX DataControl enables the window to have functionality similar to the Microsoft Windows Explorer file management tool. For example, objects corresponding to screens, views and applets are displayed with adjacent file icons, including open file icons 132 and closed file icons 134, while column and field/control objects are displayed with adjacent document icons 136. Additionally, activation of an expansion control 138 causes data pertaining to a closed folder to be expanded, while activating a collapse control 140 causes data corresponding to an opened folder to be collapsed (i.e., removed from view).

As shown in FIG. 13, a “Subscribe for Grammar” checkbox 142 is displayed below each opened screen, view, applet, and column/field/control object. Accordingly, in a block 312, the administrator selects appropriate checkboxes to identify which views, applets, and columns/fields/controls the administrator would like to provide grammar update support for. Subscription data 146 pertaining to the selected UI objects and checked options are then submitted back to metadata builder engine 114 in a block 314 along With a request to provide grammar update support for the selected UI objects. An exemplary set of subscription data is shown in the right-hand portion of FIG. 12. Finally, in a block 316, the metadata builder engine invokes style sheet builder 122 to create style sheets 148 based on the application representation and the subscription data.

Based on the UI objects selected to be voice-enabled, the style sheet builder will generate an XSLT (extensible Style sheet Language transformation) style sheet, which will filter the unselected elements form the original XML data such that only data pertaining to voice-enabled UI objects are returned to Voice application 14. As the name implies, XSLT is an XML-based language used to create style sheets that are used to transform XML documents into other types of documents and to format the output of XML documents. XSLT became a W3C Recommendation in November, 1999; the specification can be found at http://www.w3.org/TR.xslt.

XSLT style sheets are built on structures called templates. A template specifies what to look for in an input document, called the source tree, and what to put into an output document, called the result tree. XSLT style sheets are also composed of XSLT elements, which generally include the <xls:style sheet>, <xls:template>, <xsl:value-of:>, <xls:output>, <xls:element>, <xls:attribute>, <xls:attribute-set> and .<xsl:text> elements. The XSLT elements also include conditional elements, such as <xsl:if>, <xsl:choose>, elements and loop elements such as the <xsl:for-each> element. All of these elements will be familiar to those skilled in the XSLT style sheet art.

Initially, each style sheet will include a set of templates corresponding to respective UI object hierarchy positions, including an application processing template, a screen processing template, a view processing template, an applet processing template, and a LIST template. If the applet is a list applet, the set of templates will further include, an RS_HEADER template, and a COLUMN template, if the applet is an entry applet (i.e., multi-field form), the set of templates will include an RS_DATA template, a ROW template and a FIELD template. The purpose of each template is to filter out unwanted data at each hierarchy level of the XML source tree document, as will be explained below in further detail.

With reference to the flowchart of FIG. 15 in view of the XSLT style sheet layout of FIGS. 14A-C, the generation of XSLT style sheets proceeds as follows. The process begins in a block 400 in which the style sheet is initialized. In accordance with one embodiment of the invention, each XSLT style sheet will include substantially the same layout and logic at the beginning of the style sheet. This will include an XSLT header section 253, and application template 254, and a screen template 256. The application template will include a code block 260 that copies all of the values in the source tree document at the application level to the result tree document, and a decision block 262 in which a determination is made to whether a screen level exists in the source tree document. If it does, screen template 256 is called in a block 264. If the screen level doesn't exist in the source tree document, the process exits.

The code blocks in the screen template are substantially similar to those in the application template. First, style sheet code corresponding to a block 266 is used to copy all of the values at the screen level of the hierarchy to the result tree document. In a decision block 268, a determination is made to whether a view level exists in the source tree. If it does, view template 258 is called in a block 270. If it does not, the process exits.

In a block 401 of FIG. 15 the tree nodes of the application representation are traversed, beginning with the root of the tree (i.e., the application level—note the application representation tree will look somewhat like an upside-down real tree, so the root is at the top of the application representation in FIG. 12). As depicted by start and end blocks 402 and 404, the operations enclosed between these two loop end points are performed on each node as the application representation tree is traversed.

In accordance with one embodiment of the invention, a style sheet is created for each view. Accordingly, in a decision block 406, a determination is made to whether the node corresponds to a selected view (i.e., a view that is selected to be voice-enabled via the subscription data). For example, supposed that the current node being processed corresponds to a Sales Accounts View 250 node in the application representation of FIG. 12. Since the corresponding subscription data indicates that this is a view that is selected to be voice-enabled, the answer to the decision block is YES (TRUE), and the logic proceeds to a block 408 in which a new style sheet is created using a base view style sheet template. This new view template will have a layout similar to a view template 272 shown in FIG. 14A, will include a code block 257 containing logic that is used to copy all values pertaining to the view level to the result tree, and an applet template routing section 274 that is used to route the XSLT processing to an appropriate template as identified in the source tree. (It is noted that applet template routing section 274 will initially be empty, as explained in further detail below.) The logic then loops back to start loop block 402 to begin processing the next node.

If the answer to decision block 406 is NO (FALSE), the logic proceeds to a decision block 410 in which a determination is made to whether the node corresponds to a selected applet. For example, suppose that the current node is a More Info Account Entry Applet node 276 in the application representation. This node is marked as being selected to be voice-enabled, resulting in a YES result to decision block 410 and leading to a block 412 in which a new applet and child template set is generated, including an applet template, and a list template. Each applet template will include substantially the same logic that includes specific references pertaining to that applet template. In one embodiment each template has a name that specifically references the node corresponding to the template. For example, a Contacts Accounts Entry Applet Template 278 corresponding to a Contacts Accounts Entry node 280 is shown in FIG. 14B. This template includes a code block 282 containing logic to copy all of the values pertaining to the Contacts Accounts Entry Applet in the source tree to the target tree. The template further includes a code section pertaining to a decision block 284 through which a determination can be made to whether the source tree document includes a list level. The template also includes a code block 286 that contains logic to call an appropriate list template (in this case a Contacts Account Entry Applet List template 288). (It is noted that for simplicity Contacts Account Entry Applet List template 288 is used in conjunction with both the Accounts List applet and the Contact Account Entry Applet. It will be understood that in actual practice a separate List template would be provided for each applet.)

Each List template will include a code block 290 containing logic to copy all values pertaining to the list level of the source tree document. As discussed above, if an applet is a list applet, an RS_Header and a column template are added, as depicted by an Account List Applet RS_HEADER template 292 and an Accounts LIST Applet Column template 294. In contrast, if the applet is an entry applet than an RS_DATA template, row template, and field template are created, as depicted by a Contacts Account Entry Applet RS_DATA template 296, a Contacts Account Entry Applet ROW template 297, and a Contacts Account Entry Applet Field Template 298. Accordingly, each list template will include a code section corresponding to a decision block 320 by which a determination is made to whether and RS_DATA level exists in the source tree document, and/or a code section corresponding to a decision block 322 by which a determination can be made to whether an RS_HEADER level exists in the source tree document. If the answer to decision block 320 is TRUE, the logic flows to a code block 324 in which an appropriate RS_DATA template is called. If the answer to decision block 322 is TRUE, the logic flows to a code block 326 in which an appropriate RS_HEADER template is called.

As depicted by Account List Applet RS_Header template 292, each RS_Header template includes a code block 328 containing logic to copy all of the values pertaining to the applet level from the source tree to the result tree. A code section pertaining to a decision block 330 is also provided that is used to determine whether an appropriate column template exists in the source tree document. If it does, the logic proceeds to a code block 332 in which the appropriate column template is called.

As depicted by Account List Applet Column template 294, each column template will include a code block 334 that includes logic to filter out all data at the column level that does not pertain to columns that were marked to be voice enabled for the applet that is being currently processed. For example, in code block 334, logic is included to filter out data in all columns of the Account List Applet except for a Name column. When a Column template is initially generated, the filtering logic corresponding to code block 334 will be empty.

As depicted by Contacts Account Entry Applet RS_DATA template 296, each RS_DATA template includes a code block 336 that contains logic to copy all of the values pertaining to the RS_DATA level in the source tree. Each RS_DATA template also includes a code section corresponding to a decision block338 by which a determination is made to whether a Row level exists in the source tree. Each RS_DATA template further includes a code block 340 that is used to call an appropriate Row template corresponding to the Row level.

Each Row template includes a code block 342 containing logic to copy all values pertaining to the Row level of the source tree, as depicted in Contacts Account Entry Applet Row template 297. Each Row template also includes a code section corresponding to a decision block 344 by which a determination is made to whether a Field level exists in the source tree. Each Row template further includes a code block 346 that is used to call an appropriate Field template corresponding to the Row level.

In a manner similar to the column template discussed above, each field template includes a code block 348 containing logic to filter out all data at the field level that does not pertain to fields that were marked to be voice enabled for the applet that is being currently processed. For example, in code block 348, logic is included to filter out data in all fields of the Contacts Account Entry Applet except for a Last Name column, a First Name column, a City column, and a State column. When a Column template is initially generated, the logic corresponding to code block 348 will be empty.

Returning to the flowchart of FIG. 15, the next operation is performed in a block 414, wherein branch logic is created in the “parent” view template for the current applet. Generally, this branch logic will be contained within an applet template routing section 274 and comprise a choose block containing a list of test conditions. Each of these test conditions is depicted in view template 272 as a decision block 337 and a call block 339. For example, the test conditions in applet template routing section 274 pertain to applet nodes 276, 279, 281, 283, and 280 in the application representation of FIG. 12. Generally, if a test condition is determined to be TRUE, the applet template corresponding to the test condition is called.

Upon completion of block 414, the logic loops back to process the next node, which would be a name column/field node 285. This node would be processed in the manner discussed below, along with all of the other field nodes of the More Info Account Entry applet. The processing would then address Activities Account Entry applet node 279 (and subsequently its field nodes), followed by Assets Account Entry applet node 281 (and subsequently its field nodes) followed by an Attachments Account Entry applet node 282 (and subsequently its field nodes). As discussed above, an appropriate set of applet and child templates would be created for each applet node in block 412, and an appropriate portion of template branch logic will be added to the parent view template for these applets.

Now suppose that a Contacts Account Entry applet node 284 is encountered. After processing this node, the next node to be encountered is a Personal Title column/field node 287. In this instance, the answers to both decision block 406 and 410 would be NO, and the logic would proceed to a decision block 416 in which a determination is made whether the node corresponds to a selected column or field. Since the Personal Title field node is marked as not selected, the answer to decision block 416 is NO, and the logic loops back to process the next node, which is a Last Name field node 289. This time, when the logic reaches decision block 416 the result is YES (since this UI object was selected to be voice-enabled), and the logic proceeds to a block 418. In this block, XSLT code is added to the column and/or field template child of the current applet (as applicable) to enable data corresponding to the column or field to be filtered through. For example, this logic might be similar to that shown in code block 334 for a Column template, or that shown in code block 348 for a Field template.

In one embodiment, addition filter conditions are concatenated onto a first filter condition for other column or field objects corresponding to the current applet upon subsequent processing of the applets child column and field nodes as those nodes are encountered. For example, in the application representation of FIG. 12, each of the Last Name, First Name, State and City fields have been selected to provide grammar update support for. As a result, appropriate filter logic would be added to allow data pertaining to these fields to be filtered through at the Field level.

The operations and logic described above for the flowchart of FIG. 15 are further repeated until all of the nodes in the application representation have been processed. The net result is that in accordance with one embodiment of the invention there will be a separate style sheet created for each view, and each view will include child templates corresponding to one or more applets that are contained within that view.

Exemplary Enterprise Data System

In one embodiment, enterprise data system 16 comprises a Siebel 7 enterprise data system and Web engine 106 comprises a Siebel Web Engine (SWE). Under the Siebel 7 architecture, the SWE provides an XML interface to enable third party applications to access a Siebel enterprise data system. Siebel 7 supports open system architecture through XML pages that are generated by the Siebel Web Engine as applications can make a request through a web-server, Java Data Bean or ActiveX Data Control.

In order to support different implementations of voice application that vendors develop, the XML interface generates the definition of user interfaces and user data in XML format, which will then be sent to the vendor's voice application. The voice application will use this information to format its voice page and present that page to its voice users via internal operations such as TTS. In response to verbal navigation commands and data request, the voice application will then format a next request based on a current user navigation context and submit it via an appropriately configured XML document back to the Siebel Web Engine. Throughout the remainder of this specification, SWE XML interface access examples will be provided using an HTTP request format. It is important to note that similar access features are also available through an equivalent COM or JDB (Java data bean).

XML Page Content

The XML page output is based on the application definitions, including application, screen, view, applet, and columns/fields/controls, that are defined in a repository. In accordance with the Siebel enterprise data system architecture, administrators are enabled to customize their enterprise data system implementations to fit their needs such that each implementation will be unique. The XML interface defines XML tags in the XML pages to support various types of user interfaces that are presented to different type of users, including HTML and WML dat.

Generally, each XML output page 34 that is sent back to voice application 14 contains the following sections:

-   -   1. The Supported Version of XML and Encoding Information

This information is appended in all XML pages.

-   -   2. Application Information

This information is appended in all XML pages. It describes the application name, such as Siebel Sales Enterprise, that the voice application is connected to and interacting with.

-   -   3. User Agent Markup

This information is appended to all XML pages. It describes the default markup language that is supported and is based on user-agent in the http request header.

-   -   4. Active Screen, View and Applets Definition and User Data

This information is generated by default. If application only wants this information, it can add SWEDataOnly=TRUE in the http request. This section contains current active screen and view information and also applets and the record (user data) information defined in that view.

XML User Data

This section gives a detailed description of the outbound XML tags contained in an XML page 34 that is returned to voice application 14 in response to a grammar update request. To retrieve the grammar update data, Voice application 14 sends a grammar update request having a format described below to Web engine 106. The request contains UI object specific information, such as screen, view, and applet identifiers, and specifies a style sheet to use when filtering the returned dataset. The request may also include additional parameters that are specific to the Siebel Web Engine, as well as a last update value. A table listing some of these parameters and the effect of such parameters is contained in the attached appendix. For example, if the voice application only wants data returned without UI information, the user can specify that the SWEDataOnly parameter is set to TRUE in the request. When this parameter is set, the returned XML contains only data tags and does not contain any UI Navigation elements like menu drop downs, page tabs etc. In contrast, if the SWEDataOnly is not set to TRUE (default value), then in addition to the data, the user data returned includes data pertaining to the screen, applet and view the data resides in. For instance, the user data for the Contacts screen would have information pertaining to the SCREEN, VIEW, and APPLET the data is retrieved from in addition to the actual user contact data.

The sample XML provided herein represents XML data for the Contacts Screen. An HTTP request made to Web engine 106 SWE to retrieve data pertaining to the Contacts screen may have the following format:

http://localhost/sales/start.swe? SWECmd=GotoPageTab&SWEScreen= Contacts+Screen&SWEGetDataOnly=TRUE

LISTING 1

The http://localhost/sales/start.swe? Parameter specifies the Internet URL address for the Web engine. The parameters in the second line correspond to specific commands that instruct the Web engine what data is desired based on a navigation context within the application—in this case the contacts screen. As discussed above, the last parameter specifies that only data is to be returned.

In general, a typical XML page that is returned by the Web engine in response to a data request will have a format shown in FIG. 16 (when the SWEDataOnly=TRUE argument is used). As will be recognized by those skilled in the XML art, the XML page includes nested pairs of XML tags that are used to define a format for the returned data. Each pair of tags defines a level in the hierarchy of the XML tree. Detailed examples of various portions of the XML page are shown in FIGS. 17, 18, and 19.

With reference to FIG. 17, the first element in the XML page will be an application element 350 that identifies the name of the application. The next element comprises a user agent element 351 that provides information about the user agent or the browser type that made the XML or HTML request. A screen element 352 appears next, which is contained inside of the application element tag pairs. This element gives information about the name and title for the currently active screen.

The next element is a view element 354. Similar to the screen element, the view element describes the name and title of the currently active view. An applet element 356 is contained inside the view. In addition to returning an applet name 358 and applet title 359, the applet element includes a MODE attribute 360, a NO_INSERT attribute 362, NO_MERGE attribute 364, a NO_DELETE attribute 366, a NO_UPDATE attribute 368, a NO_EXEC_QUERY 370. The MODE attribute describes what mde the applet is in. It can either be in an EDIT mode or BASE mode. The former means that the applet allows modification, deletion, creation and querying of records. The latter means that the applet is read only and cannot be modified.

The NO_INSERT, NO_MERGE, NO_DELETE, NO_UPDATE, NO_EXEC_QUERY attributes provide a filter to what specific edit mode operations are possible for the applet. If any of these attributes are TRUE then that particular operation is not possible. For instance, if the NO_INSERT attribute is TRUE then new records cannot be inserted onto this applet. The voice application can tailor the voice commands based on these attributes. For instance, if the NO_EXEC_QUERY attribute is set to FALSE for an applet, this indicates that the Voice application should be able to query for a contact using that applet.

Another attribute included in the applet element is a CLASS attribute 372. This attribute specifies the C++ class the applet belongs to. For instance, in the illustrated example the CLASS attribute has a value of CSSFrameListBase, which identifies it as a List applet under the Siebel 7.0 architecture.

A ROW_COUNTER attribute 374 provides an indication of the number of data records returned. A “+” at the end of the attribute value indicates that there are more records than that returned by the current XML page. One of the ways to get all the data would be to check for the ROW_COUNTER attribute and see if it contains a “+”. If it does, then submit the prior data request to the Web engine repeatedly until the ROW_COUNTER attribute no longer ends with a “+”.

It is possible to retrieve a large number of rows via a single request by setting the SWESetRowCnt parameter in the HTTP request. Caution should be used when setting this parameters, as a large value may generate a delayed response since data pertaining to the number of rows provided by the parameter must be retrieved, converted into an XML format, and appended to the XML page.

In addition the HTTP route, XML pages that return only data may also be retreived via the. Siebel Data Bean and ActiveX Controls via calls to methods provided by the underlying business components (i.e., the business components corresponding to object manager 54). This way, specific columns can be activated directly, thus limiting the returns to specified data.

RS Header, Column

The next XML element of importance is the RS_HEADER element 376. As shown in further detail in FIG. 18, this element contains one or more COLUMN elements 378 that provide column details for the underlying data records. Each column element includes a NAME attribute 379, DISPLAY_NAME attribute 380, and a TEXT_LENGTH attribute 381 that respectively provide information about the name, title and text length of the underlying database column to which it pertains. A DATATYPE attribute 382 describes what kind of data type the column represents. For instance, a phone number might have a data type of “phone” and an email might have a data type of “email” or “character.”

A REQUIRED attribute 383 defines whether the column is a required column or not. This information is useful when creating new records. The voice application can determine what field information is mandatory by looking at this attribute. A FORMAT attribute 384 is an important attribute that the voice application can use to determine the format of the data. For the Date data type this attribute will contain the acceptable Date Format (e.g., as shown in the middle column element of FIG. 18). For revenue and other price related fields this attribute will have the format for the dollar amount. The voice application can use this to get or display the right information back to the user.

A CALCULATED attribute 385 specifies that the column is not a database column but rather contains a value that is calculated using a mathematical expressions or similar calculation. A FIELD attribute 386 provides the name of the FIELD element the column refers to. The FIELD element (described below) contains the actual data. Typically, voice application 14 might make use of both the FIELD and COLUMN elements to get more information on the data.

A READ_ONLY attribute 387 and a LIST_EDITABLE attribute 388 specify whether the column is editable or just read only. A NUMBER_BASED attribute 389 and a TEXT_BASED attribute 390 indicate whether the column or field is a number or text, respectively.

RS Data, Row, Field

The next important XML element is an RS_DATA element 391. This element contains the XML tags that hold the actual data. An example of an RS_DATA element is shown in FIG. 19.

A ROW element 392 identifies the Row id of the data in the attribute ROW_ID. This information is very useful in querying for a particular row of data and getting the detailed information for that row. For instance, if the voice application wanted a particular row, e.g. 12-WFJ4D, on the Contacts Screen, the XML request would look something like the following:

http://localhost/sales/start.swe? SWECmd=InvokeMethod&SWEMethod= DrillDown&SWEView=Visible+Contact+List+View&SWE SetMarkup=XML&SWEApplet=Contact+List+Applet&SWERowId=12− WFJ4D&SWEField=Last+Name

LISTING 2

A SELECTED attribute 393 indicates that the particular row is selected on the User Interface. FIELD elements 394 holds the actual data for the row. Each FIELD element includes a NAME attribute 395 that provides the name of the Business Component field corresponding to the element. This information is useful in determining what fields to query on while fetching a particular row id. In the URL of LISTING 2 the SWEField parameter is queried on the Last Name of the contact. Each FIELD element also includes a VARIABLE attribute 396 value that corresponds to the name of the column to which the field is mapped to.

Retrieving Detailed Information About the Data

As discussed above, the RS_HEADER section holds detailed information about each data column. For instance, if the voice application wants to detect if a particular column holds a phone number then it should lookup the DATATYPE attribute in the COLUMN element (under the RS_HEADER section) and then get the data from the FIELD element. The FIELD attribute of the COLUMN element gives a link to the FIELD element, which holds the actual data. It is recommended not to use the field attributes in the RS_DATA section for data type detection; as this information is not guaranteed to be a constant. This might change if the object definition, field names in this case, are changed.

Grammar Update Processing

The purpose of voice update support module 104 is to support grammar update for the voice application. As discussed above, the grammars are words or patterns of words that are listened for by a speech recognizer and other grammar processors that are part of the voice infrastructure and/or the voice application. The speech recognizer uses grammars to know what the user said and then passes the information to the voice application for further processing. In one respect, grammar fields are basically the subset of list columns defined in a list applet. For example, as the voice application is in the state of looking up an account, the voice user can say an account name and the speech recognizer will use the account name list that the voice user would normally view if he or she was connected to the enterprise data system via an HTML client as the grammar to understand what the voice user said. Then the voice application uses this account name to format the request and send it to the Siebel Web Engine to get the detailed information of that account.

In order to support this paradigm, grammar data corresponding to various data columns must be accessible to voice application 14. Preferably, this will be done by periodically retrieving data pertaining to those data columns from the enterprise data system via the mobile connector (or via another access means, such as a backend connection directly to database 38), and storing the retrieved data in a manner that is useable by the voice application and/or voice infrastructure 20 as grammar data, such as in grammar database 31. The specific implementation details for storing and accessing the grammar data will be familiar to those skilled in the voice access system arts and are outside the scope of the invention.

Voice update support module 104 supports dynamic grammar updates through exporting user data in XML format to the voice application. The output is generated by Web engine 110 based on the navigation context desired to provide grammar update for (e.g., view and applet) specified in the XML query request and uses grammar stylesheets to filter out information that is not required as grammars. In addition, by specifying a last update value, the voice application can periodically check if there is any new/updated data (also refered to as “delta” data) which are used for grammar, and retrieve the delta changes if desired.

The retrieval of grammar information means getting the data of the subset of the list columns in the applet to which the update is to apply. This may be implemented with a SWE method, GetVoiceGrammer, to retrieve the delta data that is based on the specified navigation context and the last update time that the periodic update was performed for that navigation context and use an appropriate grammar stylesheet (e.g., pertaining to a view) to filter the output for data only pertaining to grammars.

In one embodiment, the request parameters sent to web engine 106 for Voice Update Support should include the following information:

a. SWE Command Name, required

a. SWE Method Name, required

b. View Name, required

c. Applet Name, required

d. Last Update Time, optional

For example if a voice application submits the command with the parameters below to the Web Engine:

SWECmd=InvokeMethod SWEMethod=GetVoiceGrammar& SWEView=Account List View& SWEApplet=Account List Applet& LastUpdate=01/15/2001

Where

GetVoiceGrammar is a command in the set of SWE commands;

SWEView specifies the view name;

SWEApplet specifies the applet names that have grammar fields defined;

LastUpdate specifies the last update time that the delta is based on.

The SWE will return the list of account names that have been updated or added since Jan. 15, 2001. If the LastUpdate parameter is not provided, the voice update support module will return all grammar data pertaining to the view and applet.

In one embodiment, the output will be in XML format using the same output DTD (data type definition) normally implemented by the web engine, but it will contain only partial UI information. In case of an error during processing, the output will include the error message in an <ERROR> tag.

With reference to the flowchart of FIG. 21, a typical grammar update process will proceed as follows. In a block 440 the voice application determines which navigation contexts (e.g., views and applets) it wants to update grammar data for and formulates one or more XML grammar update request requesting these data and sending the request to the Web engine via the COM or Java interface or through the Web server using HTTP. Each request is accompanied with the name of the grammar style sheet that is to be appled and last update information, if applicable.

For example, suppose it is desired to update the Contacts Accounts Entry Applet of the Sales Accounts view and the applicable style sheet is named “Sales_Accounts_stylesheet”. Using HTTP, the XML request would look something like the following:

http://localhost/applicationname/start.swe? SWECmd=GotoView&SWEView=Sales+Accounts&SWESetMarkup= XML&SWEApplet=Contacts +Accounts+Entry+Applet&SWEDataOnly=TRUE&SWEXslStyleSheet= Sales_Accounts_stylesheet

LISTING 3

In the foregoing example and other examples discussed above, the XML request comprises a concatenated list of Siebel Web Engine commands, methods and arguments that informs the Siebel Web Engine what data is wanted and how that data is to be provided back to the requester. In general, the Web engine needs to know a navigation context for the request data, such as the screen, view, applet, and columns or fields from which the data may be accessed. In addition to the navigation context data, the input XML document should also include the name of a style sheet that is to be applied to filter the returned data. In one embodiment, this is provided in a SWEXslStyleSheet argument. In accordance with one embodiment discussed above, a style sheet is created for each view in a given application. As a result, the style sheet corresponding to the view of the desired navigation context should be used to filter data in the output XML document.

Upon receiving the XML request, in a block 442 the Web engine parses the XML document to identify the navigation context corresponding to where the data may be accessed, along with any particular data location information, such as a rowed. This information is then passed on to the object manager to service the request. The object manager then formulates an appropriate SQL query, executes the SQL query against database 38, and returns data corresponding to the query's result set to the Web engine in a block 444. If the LastUpdate parameter is provided, the SQL query will contain a query parameter to reflect the parameter. The Web engine then generates an XML document corresponding to the result set in a block 446 based, in part, on any applicable Siebel Web Engine parameters that were provided in the incoming XMLwere provided in the incoming XML query. For example, if the SWEDataOnly argument is set to TRUE, the Web engine will filter out all of the UI content corresponding to the result set.

At this point, the mobile connector applies the identified style sheet to the XML document to filter out all the data that corresponds to UI objects (e.g., columns and/or fields) that were not selected to have grammar update support for the current navigation context (i.e., current SCREEN, VIEW, and APPLET) in the XML request in a block 448. Since the style sheet is an XSLT style sheet, one of several well-known prewritten software modules that implement an appropriate XSLT style sheet processing algorithm may be used.

As discussed above, the original XML document submitted to be transformed via the XSLT style sheet is the source tree, while the resulting transformed (i.e., filtered) document comprises the result tree. In this instance, the output of block 446 comprises the source tree to which the identified XSLT style sheet is applied. To produce the result tree, the algorithm traverses the XSLT style sheet based on conditional logic contained in the style sheet, copying data from the source tree to the result tree when a corresponding copy element is encountered.

For example, returning to the style sheet of FIGS. 14A-C, the algorithm would begin at XLST header 253 and continue sequentially through the various style sheet templates using appropriate branching conditions. The first style sheet template that is encountered is application template 254, which corresponds to the “APPLICATION” level of the source tree document. As discussed above, the XML document that is output from the Web engine after the style sheet is applied will have a format similar to that shown in FIG. 16. The source tree document will have a similar format. Accordingly, the “APPLICATION” level is identified by the <APPLICATION . . . > tag. In block 260 all of the values pertaining to the application level are copied to the result tree document. For example, data pertaining to the APPLICATION NAME will be copied to the result tree.

Next, in decision block 262 it is determined that a Screen level exists in the source tree, and screen template 268 is called in code block 264. This causes the processing to jump to screen template 268.

In a manner similar to Application template 258, in the Screen template all of values pertaining to the Screen level are copied to the result tree in block 266, and a determination is made in decision block 268 to whether a View level exists in the source tree. For source trees having a structure similar to that shown in FIG. 16, the answer to decision block 268 will be true, causing View template 272 to be called in block 270.

In View template 272, things get a little more interesting. Since the selected style sheet will correspond to the current view, all of the view information is copied to the result tree in block 257, such as the views name and title. The processing will then flow to applet template routing section 274, wherein the test conditions corresponding to decision blocks 337 are evaluated. In the current example, the applet is the Contacts Account Entry Applet, which has a corresponding test condition defined in a decision block 341. In response to a TRUE result for decision block 341, code pertaining to a block 343 will be executed, causing the processing to jump to Contacts Account Entry Applet template 278.

At the start of this template, all of the applet information is copied to the result tree in block 282, leading to decision block 284, which will determine that the source tree includes a List level. Contacts Account Entry Applet List Template 288 is then called in block 268. In the Contacts Account Entry Applet List Template, data pertaining to the list level (this will usually include just the <LIST> and </LIST> tags) is copied to the result tree, and an RS_DATA test condition corresponding to decision block 320 is encountered. If this condition is TRUE, which will be the case when field data is sought, the processing jumps to Contacts Account Entry Applet RS_Data template 296 via code block 324. In this template, all values pertaining to the RS_DATA level in the source tree is copied to the result tree in block 336, and then a determination is made in decision block 338 that a Row level exists in the source tree. Accordingly, Contacts Account Entry Applet Row template 297 is called in block 340, causing the style sheet processing to advance to the Contacts Account Entry Applet Row template.

In this template, all values pertaining to the Row level of the source tree are copied in block 342 to the result tree, and it is determined in decision block 344 that a Field level exists in the source tree. Accordingly, Contacts Account Entry Applet Field template 348 is called via block 346.

The Contacts Account Entry Applet Field template is different than the previous templates that were encountered. Rather than copy all of the data to the result tree, the logic in code block 348 says to copy data in the source tree pertaining to the “Last Name,” “First Name,” “City,” and “State” fields to the result tree; the data in all of the other fields of the field templates parent applet will not be copied to the result tree, and thus will be filtered out.

Suppose that it was desired to retrieve data pertaining to the Account List Applet 275 in the application representation of FIG. 12. Since the Application, Screen, and View are the same for this applet as they were for More Info Account Entry applet 276, the processing would proceed in the same manner as discussed above until reaching Contacts Account Entry Applet List Template 288. In this instance, the result of decision block 320 will be NO (FALSE), and the logic will proceed to decision block 322, which will produce a YES (TRUE) result since a source tree corresponding to a list applet will include an RS_HEADER level. As a result, the style sheet processing will jump to Account List Applet RS_HEADER template 292 via code block 326, wherein the values pertaining to the RS_HEADER level would be copied from the source tree to the result tree in block 328. Next, in decision block 330 it would be determined that a Column level exists in the source tree. The result of this condition would be TRUE, causing the processing to finally jump to Account List Applet Column template 294, which contains a filter that will only allow data pertaining to the Name column to be copied to the result tree.

After generating the result tree, the web engine The web engine then sends the filtered data as an XML document back to the voice application in a block 450. As before, the data may be sent back using the COM or Java interface, or via the HTTP web server. The filtered data comprises the grammar update for the specified navigation context in view of the grammar update-enabled UI objects for the navigation context. If the LastUpdate parameter is used, the filtered data comprises “delta” grammar data. In either case, the filter grammar update data is used by the voice application in a block 452 to update its grammar database.

Exemplary System Infrastructure

An exemplary system infrastructure 500 by which one embodiment of the invention may be implemented is shown in FIG. 22. The enterprise data system side of system infrastructure 500 uses a well-known N-tier architecture, wherein one or more physical machines occupy each tier in the architecture. These tiers include a database tier, depicted by a database server 502, and application server tier, depicted by an application server 504, and a web server tier, depicted by a web server 506. Each of the machines in the N-tier architecture are linked in communication via a local area network (LAN) 508.

Database server 502 is used to run an RDBMS (relation database management system) database server software component that hosts database 38. The RDBMS database server software will typically comprise a SQL database server that may be provided by one of several vendors, including Oracle (Oracle Enterprise 8i and 9i), Microsoft (SQL Server 7 or 2000), IBM (DB2)Database, Sybase, or Informix. All of the components depicted in the block corresponding to application server 36 may be run in the application server tier. Optionally, all or a portion of the software associated with Web engine 110 may be run on web server 112.

On the voice application side, the architecture includes a voice application server 510 on which voice application 14 is run. The voice application server is linked to web server 508 via a computer network 512, such as a LAN, a WAN (wide area .network) or via the Internet. Generally, the voice application server will be connected to another server that is part of voice infrastructure 20 via a LAN or the same machine may be used for both voice infrastructure operations and for serving the voice application. If the Siebel COM or Java interface 110 is implemented, the client side of this software will typically be run on voice application server 510. If Web server 112 is used, software corresponding to this component may be run on the voice application server or a separate web server machine linked to the voice application server via a LAN (not shown).

Voice application server 510 is also linked to grammar database 31. In one embodiment, the grammar database is hosted by the voice application server. In another embodiment, the. grammar database is hosted on a separate database server (not shown), as is commonly done in distributed processing architectures.

As discussed above with reference to FIG. 7, in one embodiment reference or voice vendor GUI 108 is supported by Web pages that are served to a client 514 via computer network 512. Alternative, the Voice vendor may create their own GUI (108) based on a language that supports the generation of interactive graphical user interfaces, such as C, C++, or Java, in which case the GUI component may be directly connected to application server 504 via a LAN or WAN connection (not shown).

Exemplary File Server Computer System

With reference to FIG. 22, a generally conventional computer server 600 is illustrated, which is suitable for use in connection with practicing the present invention. For example, computer server 600 may be used for running application server software software modules and components, including object manager 56, data manager 58, Web engine 106, voice update support 104, and voice metadata builder 102. The same or preferably a separate computer server of similar architecture may be used to host database 38. Similarly, the same or preferably a separate computer server of similar architecture may be used for Web server 112. Examples of computer systems that may be suitable for these purposes include stand-alone and enterprise-class servers operating UNIX-based and LINUX-based operating systems, as well as servers running the Windows NT or Windows 2000 Server operating systems.

Computer server 600 includes a chassis 602 in which is mounted a motherboard (not shown) populated with appropriate integrated circuits, including one or more processors 604 and memory (e.g., DIMMs or SIMMs) 606, as is generally well known to those of ordinary skill in the art. A monitor 608 is included for displaying graphics and text generated by software programs and program modules that are run by the computer server. A mouse 610 (or other pointing device) may be connected to a serial port (or to a bus port or USB port) on the rear of chassis 602, and signals from mouse 610 are conveyed to the motherboard to control a cursor on the display and to select text, menu options, and graphic components displayed on monitor 608 by software programs and modules executing on the computer. In addition, a keyboard 612 is coupled to the motherboard for user entry of text and commands that affect the running of software programs executing on the computer. Computer server 600 also includes a network interface card (NIC) 614, or equivalent circuitry built into the motherboard to enable the server to send and receive data via a network 616.

Data storage may be implemented via a plurality of hard disks 618 that are stored internally within chassis 602, and/or via a plurality of hard disks that are stored in an external disk array 620 that may be accessed via a SCSI card 622 or equivalent SCSI circuitry built into the motherboard. Optionally, disk array 620 may be accessed using a Fibre Channel link using an appropriate Fibre Channel interface card (not shown) or built-in circuitry.

Computer server 600 generally may include a compact disk-read only memory (CD-ROM) drive 624 into which a CD-ROM disk may be inserted so that executable files and data on the disk can be read for transfer into memory 606 and/or into storage on hard disk 618. Similarly, a floppy drive 626 may be provided for such purposes. Other mass memory storage devices such as an optical recorded medium or DVD drive may also be included. The machine instructions comprising the software components that cause processor(s) 604 to implement the operations of the embodiments of the invention disclosed herein will typically be distributed on floppy disks 628 or CD-ROMs 630 (or other memory media) and stored in one or more hard disks 618 until loaded into memory 606 for execution by processor(s) 604. Optionally, the machine instructions may be loaded via network 616 as a carrier wave file.

Although the present invention has been described in connection with a preferred form of practicing it and modifications thereto, those of ordinary skill in the art will understand that many other modifications can be made to the invention within the scope of the claims that follow. Accordingly, it is not intended that the scope of the invention in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow.

APPENDIX

TABLE 1 provides and exemplary set of Siebel Web Engine (SWE) commands that enable access to a Siebel Enterprise Data System via an HTTP XML request. TABLE 2 provides various SWE methods that may be used to access the Siebel Enterprise Data System via an HTTP XML request. TABLE 3 includes parameters that may be provided for the SWE commands and methods in an HTTP request to control the form and content of a returned XML document.

TABLE 1 Command Description Required Arguments Optional Arguments GotoPageTab Go to a Siebel screen. SWEScreen - name of None Will show the default the screen view for the screen. GotoView Go to a Siebel View. If SWEView- name of the SWEKeepContext- if the SWEPPostnApplet view. TRUE, keeps the and SWEPostnRowID current business object arguments are specified, context, when it will execute a search requesting to a view for the specified rowID in based on the same the specified applet. If business object. SWEQMApplet and SWEPostnApplet- SWEQMMethod name of the applet on arguments are specified, which the search it will invoke the method should executed. after going to the view. SWEPostnRowId- row Id to search for. SWEQMApplet-name of the QueueMethod applet. This is the applet where the method specified in SWEQMMethod should be invoked after going to the view. SWEQMMethod-name of the QueueMethod method. The method to be invoked. SWEQMArgs- arguments of the QueueMethod method. InvokeMethod Invoke a method on an SWEMethod-name of the SWEService-name of applet, a business method. the business service to service, a business invoke the method. component, or the SWE SWEBusComp-name application. of the business The optional component to invoke SWEService, the method. SWEBusComp, and SWEApplet-name of SWEApplet arguments the applet to invoke the are used to specify the method. Siebel object on which the method should be invoked.

TABLE 2 Method Description Required Arguments Optional Arguments CopyRecord Performs initialization None None then calls CopyRecord on the business component. CreateRecord Performs initialization, None None then calls NewRecord on the business component. Drilldown Drilldown on the field as SWEField: Specify the None specified in the name of the applet field argument SWEField. that you want to drilldown on. The drilldown information is specified in the repository. EditRocord Edit a record. None SWESeq: Specify the sequence number of the Edit template to show. You can have many Edit templates for an applet in Siebel Tools, each identified by the sequence number. ExecuteQuery Execute a query. The None List of arguments with query spec of the fields name and value, where is specified in the list of the name specifies the arguments. field name and the value specifies the field query spec. Will set field query spec before executing the query. GotoView Go to a Siebel view. SWETargetView-name SWEKeepContext-if If the SWEPostnApplet of the view. TRUE, keep the current and SWEPostnRowId business objects if arguments are specified, going to a view that will execute a search for uses the same the specified rowed in business object. the specified applet. SWEPostnApplet, name of the applet that the search should be executed on. SWEPostnRowId- rowId to search for. SWEQMApplet-name of QueueMethod applet. This is the applet where the method (as specified in SWEQMMethod) should be invoked after going to the view. SWEQMMethod-name of the QueueMethod method. The method to be invoked. SWEQMArgs- arguments of the QueueMethod method. NewRecord If the applet has an None None association applet, show the association popup applet. Otherwise, create a new record.

TABLE 3 Query Parameter Description Usage Example SWEGetApplet This parameter is used 1. SWEGetApplet=<name 1. SWEGetApplet=Account+ to filter the outbound of the applet> List+Applet XML document so only 2. <ARG 2. <ARG the applet named as the NAME=”SWEGetApplet”> NAME=”SWEGetApplet”> value of the parameter name of the Account List will be allowed in the applet</ARG> Applet</ARG> output. All other document content will be discarded. SWESetMarkup Temporarily set the 1. SWESetMarkup=<name 1. SWESetMarkup= markup language to use of the markup HTML in the output document. language> 2. <ARG 2. <ARG NAME=”SWESetMarkup”> NAME=”SWESetMarkup”> HTML</ARG> markup language</ARG> SWESetRowCnt Temporarily set the 1. SWESetRowCnt= 1. SWESetRowCnt= workset size or row <number of list rows> 50 number of list applets in 2. <ARG 2. <ARG the view. NAME=”SWESetRowCnt”> NAME=”SWESetRowCnt”> number of list number of rows</ARG> list rows</ARG> SWESetNoTempl Disable the use of 1. SWESetNoTempl= 1. SWESetNoTempl= templates during the {TRUE | FALSE} TRUE generation of the 2. <ARG 2. <ARG outbound document. NAME=”SWESetNoTempl”> NAME=”SWESetNoTempl”> TRUE|FALSE TRUE</ARG> </ARG> SWEDataOnly Discard all UI content 1. SWEDataOnly={TRUE | 1. SWEDataOnly= (including anchors) if set FALSE} TRUE to TRUE. 2. <ARG 2. <ARG NAME=”SWEDataOnly”> NAME=”SWEDataOnly”> TRUE|FALSE</ARG> TRUE</ARG> SWEXslStyleSheet Specify the name of the 1. SWEXslStyleSheet= 1. SWEXslStyleSheet=ui.xsl XSLT stylesheet to use <stylesheet name>. 2. <ARG to perform the XSLT on The stylesheet needs NAME=”SWEXslStyleSheet”> the XML output to be in the ui.xsl</ARG> document. application's webtempl directory. 2. <ARG NAME=”SWEXslStyleSheet”> name of the XSLT stylesheet</ARG> 

1. A computer-implemented method comprising: receiving a grammar update request from a voice access system, wherein the grammar update request identifies a navigation context of a user interface provided by a data system, and the user interface provides access to information in the data system; retrieving data, from the data system, pertaining to the navigation context; filtering the data to obtain filtered data pertaining to user interface (UI) objects enabled for grammar updates; and providing the filtered data to the voice access system.
 2. The method of claim 1, wherein the grammar update request comprises information identifying a last update for the navigation context, the filtering further comprising: filtering the data such that the filtered data correspond to changes since the last update.
 3. The method of claim 1, wherein the grammar update request comprises an extended markup language (XML) document.
 4. The method of claim 1, wherein the grammar update request comprises commands to access the data system via an application program interface (API).
 5. The method of claim 4, wherein the API comprises a Siebel Web Engine API.
 6. The method of claim 1, wherein the filtering comprises: generating a source tree extended markup language (XML) document that comprises an initial set of data retrieved from the data system in response to the grammar update request; and applying an extensible style sheet language transformation (XSLT) style sheet to the source tree XML document to produce a result tree XML document comprising a filtered set of data.
 7. The method of claim 1, further comprising: presenting indicia corresponding to respective UI objects of the user interface in a selection interface; and enabling a selection of UI objects to be enabled for grammar updates via the selection interface.
 8. The method of claim 7, wherein the selection interface comprises a graphical user interface (GUI) through which the indicia corresponding to the respective UI objects are presented to a user as a hierarchical tree corresponding to a hierarchical relationship of the UI objects in the user interface.
 9. The method of claim 8, further comprising: storing metadata corresponding to the user interface, the metadata comprising object definitions for the UI objects of the user interface and comprising a hierarchical position of each UI object within the user interface; processing the metadata to build an application representation comprising an internal representation of the user interface of the data system and comprising data identifying the hierarchical position of each UI object; and rendering a hierarchical tree to provide a visual representation of the application representation.
 10. The method of claim 9, wherein the application representation comprises an XML tree, the method further comprising: sending the XML tree to a browser operating on a client machine linked in communication with the data system; and rendering the hierarchical tree via the browser.
 11. The method of claim 1, wherein the UI objects comprise objects pertaining to screens, views, applets, columns, and fields in the user interface of the data system.
 12. The method of claim 1, wherein the filtered data are provided to the voice access system as an XML document.
 13. The method of claim 1, wherein the grammar update request comprises size indicia identifying a number of records to be returned to the voice access system at one time, and additional records indicia are provided with the filtered data in an event in which a number of records for a given grammar update request exceeds the number of records specified in the size indicia.
 14. The method of claim 1, wherein the data system provides a web interface having a uniform resource locator (URL) address, and the grammar update request is received via a computer network using the Hypertext Transport Protocol (HTTP) or Hypertext Transport Protocol Secured (HTTPS) protocol.
 15. The method of claim 1, wherein the grammar update request corresponds to a component object model (COM) interface provided by the data system.
 16. The method of claim 15, wherein the COM interface enables selected data to be retrieved from a database in which data for the data system are stored by referencing a business component that is used to access one or more database tables in which those data are stored, and the data system comprises a Siebel Enterprise data system.
 17. A computer program product comprising: a computer readable storage medium on which a plurality of machine-executable instructions are stored, wherein the machine-executable instructions are configured to direct a method by performing the operations of: receiving a grammar update request from a voice access system, wherein the grammar update request identifies a navigation context of a user interface provided by a data system, and the user interface provides access to information in the data system; retrieving data, from the data system, pertaining to the navigation context; filtering the data to obtain filtered data pertaining to user interface (UI) objects enabled for grammar updates; and providing the filtered data to the voice access system.
 18. The computer program product of claim 17, wherein the grammar update request comprises information identifying a last update for the navigation context, the filtering further comprising: filtering the data such that the filtered data correspond to changes since the last update.
 19. The computer program product of claim 17, wherein the grammar update request comprises at least one of an extended markup language (XML) document or a command to access the data system via an application program interface (API).
 20. The computer program product of claim 17, wherein the filtering comprises: generating a source tree extended markup language (XML) document that comprises an initial set of data retrieved from the data system in response to the grammar update request; and applying an extensible style sheet language transformation (XSLT) style sheet to the source tree XML document to produce a result tree XML document comprising a filtered set of data.
 21. The computer program product of claim 17, wherein the machine-executable instructions are further configured to perform the operations of: presenting indicia corresponding to respective UI objects of the user interface in a selection interface; and enabling a selection of UI objects to be enabled for grammar updates via the selection interface.
 22. The computer program product of claim 21, wherein the selection interface comprises a graphical user interface (GUI) through which the indicia corresponding to the respective UI objects are presented to a user as a hierarchical tree corresponding to a hierarchical relationship of the UI objects in the user interface.
 23. The computer program product of claim 22, wherein the machine-executable instructions are further configured to perform the operations of: storing metadata corresponding to the user interface, the metadata comprising object definitions for the UI objects of the user interface and comprising a hierarchical position of each UI object within the user interface; processing the metadata to build an XML tree comprising an internal representation of the user interface of the data system and comprising data identifying the hierarchical position of each UI object; sending the XML tree to a browser operating on a client machine linked in communication with the data system; and rendering a hierarchical tree to provide a visual representation of the XML tree via the browser.
 24. The computer program product of claim 17, wherein the UI objects comprise objects pertaining to screens, views, applets, columns, and fields in the user interface of the data system, and the filtered data are provided to the voice access system as an XML document.
 25. The computer program product of claim 17, wherein the grammar update request comprises size indicia identifying a number of records to be returned to the voice access system at one time, and additional records indicia are provided with the filtered data in an event in which a number of records for a given grammar update request exceeds the number of records specified in the size indicia.
 26. The computer program product of claim 17, wherein the data system provides a web interface having a uniform resource locator (URL) address, and the grammar update request is received via a computer network using the Hypertext Transport Protocol (HTTP) or Hypertext Transport Protocol Secured (HTTPS) protocol.
 27. The computer program product of claim 17, wherein the grammar update request corresponds to a component object model (COM) interface provided by the data system, and the COM interface enables selected data to be retrieved from a database in which data for the data system are stored by referencing a business component that is used to access one or more database tables in which those data are stored, and the data system comprises a Siebel Enterprise data system. 